Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kingston upon Thames

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

entity: 19207358

reference
101
name
tree-preservation-order

undefined

Laurel Grove and Coombe Glen Coombe Hill Road Kingston Upon Thames KT2 7DU
tree-preservation-zone-type
group
geometry
MULTIPOLYGON (((-0.259164 51.419174,-0.259166 51.419161,-0.259166 51.419146,-0.259163 51.419130,-0.259156 51.419115,-0.259147 51.419101,-0.259122 51.419097,-0.259100 51.419099,-0.259089 51.419104,-0.259079 51.419114,-0.259076 51.419119,-0.259074 51.419128,-0.259082 51.419136,-0.259079 51.419143,-0.259073 51.419149,-0.259063 51.419147,-0.258992 51.419128,-0.259001 51.419105,-0.258999 51.419096,-0.258990 51.419081,-0.258963 51.419060,-0.258895 51.419031,-0.258427 51.418918,-0.258410 51.418920,-0.258400 51.418943,-0.258319 51.418930,-0.258311 51.418911,-0.258293 51.418892,-0.258002 51.418809,-0.257823 51.418762,-0.257649 51.418713,-0.257534 51.418671,-0.257522 51.418666,-0.257504 51.418654,-0.257486 51.418637,-0.257465 51.418614,-0.257455 51.418600,-0.257451 51.418590,-0.257415 51.418527,-0.257390 51.418480,-0.257381 51.418457,-0.257365 51.418451,-0.257348 51.418452,-0.257227 51.418493,-0.258125 51.419280,-0.258280 51.419418,-0.258336 51.419465,-0.258563 51.419414,-0.258753 51.419364,-0.258760 51.419374,-0.258959 51.419294,-0.259058 51.419267,-0.259079 51.419259,-0.259116 51.419238,-0.259140 51.419217,-0.259156 51.419194,-0.259164 51.419174)))
point
POINT (-0.25831 51.419074)
notes
entry-date
2018-12-18
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Royal Borough of Kingston upon Thames’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL